Repository navigation
Conversation
Set the version to 0.7.0 in Cargo.toml and Cargo.lock, and regenerate the attributions, which list the app's own version. Update the places that name the current version: the opening of docs/architecture.md, the bug-report template's placeholder, the release examples in packaging/README.md, and the Last reviewed line of ACCESSIBILITY.md, which named this release as the one after 0.6.0. The About window picture in section 9.4 of docs/architecture.md shows the version, so it is retaken with this build, cut at the same place: only the version's digit differs from the earlier picture. Its alt text and the section's note on where its pictures come from say 0.7.0. This is 0.7.0 rather than 0.6.1 because the library's public API changed incompatibly since 0.6.0: Reason has new variants, Vehicle has new fields, one of them crate-private, and Plan, CoopStats and CoopManager have new public fields. Signed-off-by: Jim Schreckengast <schreck@gmail.com>
schreck61
enabled auto-merge (rebase)
November 16, 2026 06:47
schreck61
disabled auto-merge
November 16, 2026 06:51
Merged
Owner
Author
|
Replaced by #29, which has the same files and a commit message that counts only the API changes that are incompatible (Reason's new variants and the new fields of Plan and CoopStats). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Sets the version to 0.7.0 for the next release.
packaging/licenses.shbecause it lists the app's own version.TS_ABOUT=1, as Appendix A of docs/architecture.md lists it) and cut at the same place. Only the version's digit differs from the earlier picture. Its alt text and §9.4's note on where the pictures come from say 0.7.0.Why 0.7.0
Since 0.6.0,
mainhas gained failures at the cooperative crossing (#25), overlap counts in bench's strategy tables (#24), a fix that keepstrainfrom writing outside its weights folder (#27), and async-executor 1.14.1 (#26). Every package released so far was built with async-executor 1.14.0, which was yanked for a use-after-free. So far only the browser version, which is rebuilt frommain, has these changes.The library's public API also changed incompatibly:
Reasonhas the new variantsEmergency,StrandedandDisabled.Vehiclehas the new fieldsdisabledand the crate-privateblind_until, so other crates can no longer build one with a struct literal.Plan,CoopStatsandCoopManagerhave new public fields, andPlanKindis a new public enum.GOVERNANCE.md commits to Semantic Versioning, so this release is 0.7.0 rather than 0.6.1. Nothing changes for weights files: the code that reads and writes them is the same as in 0.6.0.
After merging
Tag the merged commit
v0.7.0and push the tag, as in packaging/README.md's Making a release. The release workflow builds and signs every package into a draft release, which is reviewed and then published. Publishing also sends the crate to crates.io.Testing
On Rust 1.100.0, the version CI uses:
cargo fmt --all --check, and for fuzz/cargo clippy --locked --release --all-targets -- -D warnings, and its wasm32 counterpartcargo test --locked --releasepackaging/licenses.sh --checkcargo deny --locked check